home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 23
/
Aminet 23 (1998)(GTI - Schatztruhe)[!][Feb 1998].iso
/
Aminet
/
dev
/
amos
/
AMOS1097.lzh
/
AMOSLIST
/
000031_amos-request@svcs1.digex.net_Thu Oct 2 01:27:01 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-11-02
|
2KB
Received: from svcs1.digex.net (svcs1.digex.net [204.91.197.224])
by mail2.access.digex.net (8.8.5/8.8.5) with ESMTP id BAA21033
for <mcox@access.digex.net>; Thu, 2 Oct 1997 01:27:00 -0400 (EDT)
Received: (from daemon@localhost)
by svcs1.digex.net (8.8.5/8.8.5) id XAA15703
for amos-out; Wed, 1 Oct 1997 23:29:50 -0400 (EDT)
Received: from mail3.access.digex.net (mail3.access.digex.net [205.197.247.4])
by svcs1.digex.net (8.8.5/8.8.5) with ESMTP id XAA15700
for <amos-list@svcs1.digex.net>; Wed, 1 Oct 1997 23:29:49 -0400 (EDT)
Received: from mail.mel.aone.net.au (mail.mel.aone.net.au [203.12.176.157])
by mail3.access.digex.net (8.8.5/8.8.5) with ESMTP id XAA21012
for <amos-list@access.digex.net>; Wed, 1 Oct 1997 23:29:46 -0400 (EDT)
Received: from magnet.com.au (d101-1.cpe.Sydney.aone.net.au [203.12.186.101])
by mail.mel.aone.net.au (8.8.6/8.8.6) with SMTP id NAA16842;
Thu, 2 Oct 1997 13:29:30 +1000 (EST)
From: Rod Whiteley <rwhiteley@magnet.com.au>
Reply-To: Rod Whiteley <rwhiteley@magnet.com.au>
To: Pietro Ghizzoni <ghizzo@agonet.it>,
"Mr. Giark To You" <joehick@golden.net>,
Amos-List <amos-list@access.digex.net>, mushypd@redrose.net
Date: Thu, 02 Oct 1997 13:27:13 +1000
Message-ID: <yam7214.651.270455624@mail01.mel.magnet.com.au>
In-Reply-To: <yam7209.2103.2014823272@mail.agonet.it>
X-Mailer: YAM 1.3.4 [020] - Amiga Mailer by Marcel Beck
Organization: Mitchell & Whiteley Physiotherapy
Subject: GUIExt
MIME-Version: 1.0
Content-Type: text/plain
Status: O
X-Status:
Just a quick question for the GUIExt Experts:
I'm currently porting all of the AMOSPro apps I use here at work to use the
GUIExt. This means that I currently need to use standard AMOSPro and
AMOSPro+GuiExt alternately. My problem is there seems to be no way to end a
programme, and kill AMOSPro altogether (to give control back to the workbench
with no trace of AMOSPro still running). Sure I can hide the AMOSProit when it
finishes, but if someone starts another app from the workbench, then AMOS is
still in the background (at the editor displaying the last line of the prog.)
This would be O.K. but AMOSPro doesn't let me do this reliably (disc access
always means a crash), and I guess I'm chewing up a whole bunch of memory each
time. What to do?
TIA,
Rod
By and by, how do I get a hold of v1.63?
--
Mitchell & Whiteley Physiotherapy.